:: Metaj on Mono ::Jay Metaj's trip through Linux & Mono. | ||||||||
| :: welcome to Metaj on Mono :: bloghome | contact :: | ||||||||
|
:: Thursday, January 09, 2003 :: Continued to bang my head against the "build the kernel yourself" thing. I have been able to make everything, but the bzdisk part didn't succeed, so I wasn't able to make a boot floppy. When I get another machine, I'll set up LILO or GRUB and get rid of the floppy problem.:: Tuesday, January 07, 2003 :: Kernel compiling. Going to bed and check on it in the morning. Yehaa! Taking a detour tonight on building & patching the kernel. I'll try to patch sources up to 2.4.20, build, and attempt to boot. I boot from floppy (machine has XP, don't want to disrupt my families computer usage, etc) which will be good and bad. It will be good since I can always use my 2.4.18 floppy if this build doesn't work; it's bad since I have to correctly configure the new 2.4.20 floppy. Played around with several issues tonight. The main hang-up at this point is that I can't use NUnit or any of the mono tests.:: Monday, January 06, 2003 :: Upgraded kernel to 2.4.18-19.7.x (I think that's right). Someday I'm going to tinker with building the kernel from source so I can live on the bleeding edge.:: Sunday, January 05, 2003 :: I didn't work any last night, so I just tried to re-sync option from Friday night. Amazingly it actually worked. I have successfully built, installed, compiled a simple C# app, and executed it with mono tonight. All this in the span of about 20 minutes of sporadic work on this computer. Funny how things come together some times.:: Saturday, January 04, 2003 :: I think I've completely toasted my Mono config. Either that or someone made some bad CVS check-ins. I sync'd to the CVS tree and tried to build everything -- make fails in doc/mono/runtime.:: Friday, January 03, 2003 :: 'Make' seems to work, but 'make install' does not. I'm going to get some sleep for work tomorrow. I am following H. Hettema's Beginner's from Mono Project site. So far I have successfully configured Mono package and am in the process of making and installing. In order to understand *nix base security, my login account is only a member of users group. Every time I make a little advancement (config, build, etc.) I have to spend a bunch of time decyphering errors, chmod'ing files and dirs, etc. There is probably a best practice for this kind of stuff, but I've just been giving r/w to Users group on pieces that I need. For this Mono stuff, I should probably have a group for devs which owns or has appropriate group permissions; regular users would only have read access.:: Thursday, January 02, 2003 :: Spent a bit of time thrashing around with Mono on Linux. I'm still fairly confused since I'm very much a beginner on Linux. For example, tonight I figured out how to set and echo env vars, how to create sym links, etc. Seems like I'm still very much in Basics mode.
|
|||||||
|
|
||||||||